System and Method for Pre-Marshalling Messages in an Electronic Trading Environment

ABSTRACT

System and methods for pre-marshalling messages in an electronic trading environment are provided. Specifically, pre-marshalling messages allows for client and network devices to create messages in response to a defined first condition. Pre-marshalling messages allows a trading system to do more processing up front before the message is needed and when a second condition is satisfied. Thus, when the message is needed no further or very little processing must be performed to generate and send the message. The client and/or network device may allocate a separate, unused, or under-utilized processing thread to the task of creating pre-marshalled messages. Pre-marshalled messages may be stored in memory at the network device until it is determined that the second condition has been satisfied. Once a pre-marshalled message is sent, the unused pre-marshalled messages that were stored in memory may be deleted or may be overwritten with newly pre-marshalled messages.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/769,048, filed Jun. 27, 2007, the contents of which are fullyincorporated herein by reference for all purposes.

FIELD OF INVENTION

The present invention is directed to electronic trading. Morespecifically, the present invention is directed towards pre-marshallingmessages in an electronic trading environment.

BACKGROUND

Electronic trading refers to a trading system that matches orders by anelectronic trading platform. Current examples of electronic tradingplatforms include the Chicago Mercantile Exchange (“CME”) Globex®trading system, the Chicago Board of Trade (“CBOT”) e-cbot, and Eurex,just to name a few. A trading system that matches orders electronicallyis also referred to herein as an “electronic exchange.” Exchanges likethe CME and CBOT currently offer trading via open outcry in addition toelectronic trading.

With respect to electronic exchanges, traders connect to an electronictrading platform by way of a communication link through their clientdevices. Once connected, traders select which tradeable objects theywish to trade. As used herein, the term “tradeable object” refers toanything that can be traded with a quantity and/or a price. It includes,but is not limited to, traded events, goods and/or financial productssuch as stocks, options, bonds, futures, currency, and warrants, as wellas funds, derivatives and collections of the foregoing, and all types ofcommodities, such as grains, energy, and metals. The tradeable objectmay be “real,” such as products that are listed by an exchange, or“synthetic,” such as a combination of real products that is created bythe user. A tradeable object could actually be a combination of othertradeable objects, such as a class of tradeable objects.

The messages communicated between the electronic exchange and the clientdevice include market information, as well as orders, quotes,acknowledgements, fills, cancels, deletes, cancel and replace, and otherwell-known financial transaction messages. Although the amount or typeof market information published by each exchange often differs, thereare some standard pieces of information. Market information may includedata that represents just the inside market which refers to the lowestsell price (best ask) and the highest buy price (best bid) at particularpoint in time. Market information may also include market depth, whichrefers to quantities available at the inside market and can also referto quantities available at other prices away from the inside market.

Maintaining a high level of performance and providing the most up todate market information is a challenge even for most current tradingsystems. The amount of messages sent between a client device and anelectronic exchange can be numerous and with the increase in popularityof electronic trading, the volume of messages will continue to increase.Due to the increasing amount of messages sent, received, and processedfrom an electronic exchange or a network device or a client device, thecentral processing unit (CPU) capabilities at the network and clientdevices are extremely overburdened and the network connections andnetwork speed may be overwhelmed or jeopardized by the message traffic.

In an industry where speed is of the utmost importance, overwhelmed andover-burdened network and client devices can be extremely detrimental toa trader and can possibly cost the trader profits. It is desirable fortrading systems to send and receive messages with the most up to dateand accurate information at all times. However, instead of providing thetrader with messages containing near real-time information regarding themarket, orders, etc. many current trading systems have succumbed to anincreased delay in processing capabilities.

It is therefore, beneficial to provide a trading system that offers amore efficient method for communicating messages in an electronictrading environment.

SUMMARY

To address these and other objectives, the example embodiments comprisesystem and methods for pre-marshalling messages in an electronic tradingenvironment. Pre-marshalling a message is directed to the early creationof a message before it is actually needed by a trading system.Specifically, pre-marshalling messages allows for client and networkdevices to anticipate and create messages in response to a definedcondition, such as an action by the trader or a message received fromthe client device. Pre-marshalling messages also allows a trading systemto do more processing up front, such that when the message reply ormessage request is needed the client or network device has alreadyanticipated a response, and no further or very little processing must beperformed by the client or network device. Faster processing of messagesalso leads to many advantages for the trader such as better queueposition, faster response time to market changes, etc. Determining whento send a pre-marshalled response may be user-configurable.

According to an example embodiment, trading systems may anticipate thetypes of messages that need to be created based on a satisfied firstcondition, such as the action by the trader, fill information associatedwith an order, or a message request received. For example, as soon asthe trader selects a contract to trade, the trading system will have theinformation that is needed to pre-marshal an order request message, aninside market request message, or even a market depth request messagefor that contract. When one of these messages is anticipated to be sentto the network device, such as when the first condition is satisfied,the trading system creates the pre-marshalled message with the specificmarket information known at that time and then sends the completemessage to the network device based on a second defined condition. Asecond condition might include the receipt of another message, replyfrom the network device, a submission of an order request, an ordergetting filled, submission of a delete order, updated marketinformation, or the need for an acknowledgement or error message.Although the amount of messages sent between a client device and anetwork device may not necessarily differ, the speed at which themessages are anticipated, created, and sent may be significantlyincreased.

Another example defined first condition may be a trader logging into thetrading system or perhaps boot up of a computer device such as a clientor network device. The trading system anticipates the types of messagesthat may be pre-marshalled based on past trading history orconfiguration files. Specifically, there are many types of traders thattrade the same products or types of products on a regular basis. In thisinstance, the trading system may anticipate the messages to pre-marshalland some of the information to seed the pre-marshalled messages withbased on either near term or long term history or configuration files.For example, if the trader is trading the same contract as the previousday, the pre-marshalled messages can all be seeded with the contracttype, exchange name, etc. Once further information is known for aspecific pre-marshalled message, such as if the second condition isdefined as an order request or an order deletion/cancellation, thatinformation may be added to the pre-marshalled message before it issent.

In another example embodiment, if the first condition is defined as whenthe network device receives an order request message from a clientdevice, the network device can anticipate the need for a message andpre-marshall an order accept reply message and/or an order reject replymessage that may be sent back to the client device when a secondcondition is satisfied. In this instance, where no further marketinformation needs to be added to the pre-marshalled message, the secondcondition may simply be the need for a message, at which time thepre-marshalled message is sent. The trading system is programmed to knowthat, once the network device passes the order request onto theelectronic exchange, the electronic exchange will send back either anaccept or reject message. Pre-marshalled reply messages will be ready tosend to the client device as soon as they are needed, such as when thesecond condition is defined as a response that is received from theelectronic exchange, instead of the network device using systemresources and processing power to create the full message at a laterpoint in time. The network device may also send out a pre-marshalledmessage with more up-to-date market information is received from theelectronic exchange. Alternatively, the network device may alsoanticipate messages that may be pre-marshalled before being sent to theelectronic exchange. Pre-marshalling a message request or reply mayinclude the client and network devices allocating a separate, unused, orunder-utilized processing separate thread to begin creating possiblemessages.

According to the example embodiments, a pre-marshalled message may bestored in memory at the client or network device until the mainprocessing is completed and any new information that should be added tothe message is known. Specifically, the pre-marshalled message may bestored until the first and/or second conditions are satisfied. Forexample, a message request may be sent by a client device for updatedmarket information. As soon as the trader selects the contract for whichthe updated market information is needed, such that the first conditionis satisfied, the client device may pre-marshall the message request sothat it is ready to be sent to the network device even before the traderhas made the command to send the message. The anticipated pre-marshalledmessage request is stored in memory until the second condition issatisfied, and the message is ready to be sent to the network device.Once received at the network device, a message reply may also beanticipated and pre-marshalled with the updated market information knownat that time, while waiting for the rest of the market information fromthe electronic exchange. Once the updated market information is receivedfrom the electronic exchange, thereby satisfying the second definedcondition, the updated market information is appended to the alreadypre-marshalled message waiting in memory to be sent back to the clientdevice.

Alternatively, the network device may send a preliminary messageresponse to a message request with the limited market information thatis known at that current time. Once further information is known, thecorrected or updated market information is sent to the client device asan additional message in the form of a final message response. Thepreliminary and the final messages may, for example, be associated toone another based on a unique ID or unique order key. A uniqueidentifier would allow the trading system to correctly associate theexact information to include in a final message based on the informationthat was included in the preliminary message. Sending only the correctedor updated market information to the client device in a final messagemay decrease processing time as well as decrease the size of messages.

The above example system and method illustrates a way to pre-marshallmessages in an electronic trading environment. Other examples areprovided herein. Modifications may also be made to the system andmethods without departing from the spirit or scope of the invention.Additional features and advantages of the example embodiments will beset forth in the description that follows. The features and advantagesof the example embodiment may be realized and obtained through theembodiments particularly pointed out in the appended claims. These andother features will become more fully apparent from the followingdescription and appended claims, or may be learned by the practice ofthe example embodiments as set forth hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments are described herein with reference to the followingdrawings, in which:

FIG. 1 illustrates a trading system for electronic trading according toan example embodiment, wherein the trading system includes a tradingstation where a trader can submit bids and offers for a tradeable objectbeing traded at an electronic exchange;

FIG. 2 illustrates another trading system for electronic tradingaccording to another example embodiment, wherein this trading systemincludes a trading station where a trader can submit bids and offers fora tradeable object being traded at more than one electronic exchange;

FIG. 3 illustrates a data flow diagram that demonstrates an example flowof information between the elements shown in FIGS. 1 and 2; and

FIG. 4 is a flow chart illustrating an example method forpre-marshalling messages in an electronic trading environment.

DETAILED DESCRIPTION I. A First Example Trading System

FIG. 1 illustrates an example electronic trading system in which theexample embodiments may be employed. However, it should be understoodthat the example embodiments could be equally applicable in differentembodiments and in relation to different systems as well, such as byother computer programs or systems that do not necessarily relate toelectronic trading (e.g., operating systems, gaming systems, and/orother software applications). In this example, the trading systemcomprises a client device 102 that accesses an electronic exchange 104through a gateway 106. Router 108 is used to route messages between thegateway 106 and the electronic exchange 104. The electronic exchange 104includes a computer process (e.g., the central computer) that matchesbuy and sell orders sent from the client device 102 with orders fromother client devices (not shown). The electronic exchange 104 may listone or more tradeable objects for trading. While not shown in FIG. 1 forthe sake of clarity, the trading system may include other devices thatare specific to the client site like middleware and security measureslike firewalls, hubs, security managers, and so on, as understood by aperson skilled in the art.

Regardless of the types of order execution algorithms used, theelectronic exchange 104 provides market information to the subscribingclient device 102. Market information may include data that representsjust the inside market. The inside market is the lowest sell price (bestask) and the highest buy price (best bid) at a particular point in time.Market information may also include market depth. Market depth refers toquantities available at the inside market and can also refer toquantities available at other prices away from the inside market. Thequantity available at a given price level is usually, although notnecessarily, provided by the host exchange in aggregate sums. In otherwords, an exchange usually provides the total buy quantity and the totalsell quantity available in the market at a particular price level in itsdata feed. The extent of the market depth available to a trader usuallydepends on the exchange. For instance, some exchanges provide marketdepth for all (or most) price levels, while some provide only quantitiesassociated with the inside market, and others may provide no marketdepth at all. Additionally, the exchange 104 can offer other types ofmarket information such as the last traded price (LTP), the last tradedquantity (LTQ), and order fill information.

The computer employed as the client device 102 generally can range froma hand-held device, laptop, or personal computer to a larger computersuch as a workstation with multiple multiprocessors. Generally, theclient device 102 includes a monitor (or any other output device) and aninput device, such as a keyboard, a trackball, and/or a two orthree-button mouse to support click based trading, if so desired. Oneskilled in the art of computer systems will understand that the presentexample embodiments are not limited to any particular class or model ofcomputer employed for the client device 102 and will be able to selectan appropriate system.

The network device employed as the gateway 106 generally can range froma personal computer to a larger or faster computer. Generally, thegateway 106 may additionally include a monitor (or any other outputdevice), input device, and access to a database, if so desired. Oneskilled in the art of computer systems will also understand that thepresent example embodiments are not limited to any particular class ormodel of computer(s) employed for the gateway 106 and will be able toselect an appropriate system.

It should be noted that a computer system that may be employed here as aclient device or a network device or gateway generally includes acentral processing unit, a memory (a primary and/or secondary memoryunit), an input interface for receiving data from a communicationsnetwork, an input interface for receiving input signals from one or moreinput devices (for example, a keyboard, mouse, etc.), and an outputinterface for communications with an output device (for example, amonitor). A system bus or an equivalent system may providecommunications between these various elements.

In general, it should be understood that the devices described hereincould include hardware objects developed using integrated circuitdevelopment technologies, or yet via some other methods, or thecombination of hardware and software objects that could be ordered,parameterized, and connected in a software environment to implementdifferent functions described herein. Also, the hardware objects couldcommunicate using electrical signals, with states of the signalsrepresenting different data.

It should also be noted that the client device 102 generally executesapplication programs resident at the client device 102 under the controlof the operating system of the client device 102. Also, the gateway 106executes application programs resident at the gateway 106 under thecontrol of the operating system of the gateway 106. In other embodimentsand as understood by a person skilled in the art, the function of theapplication programs at the client device 102 may be performed by thegateway 106, and likewise, the function of the application programs atthe gateway 106 may be performed by the client device 102.

The actual electronic trading system configurations are numerous, and aperson skilled in the art of electronic trading systems would be able toconstruct a suitable network configuration. For the purposes ofillustration, some example configurations are provided to illustratewhere the elements may be physically located and how they might beconnected to form an electronic trading system. These illustrations aremeant to be helpful to the reader, and they are not meant to belimiting. According to one example illustration, the gateway device maybe located at the client site along with the trading station, which isusually remote from the matching process at the electronic exchange.According to this instance, the trading station, the gateway, and therouter may communicate over a local area network, and the router maycommunicate with the matching process at the electronic exchange over aT1, T3, ISDN, or some other high speed connection.

In another example illustration, the client site may be located on theactual grounds of the electronic exchange (for example, in the buildingof the exchange). According to this instance, the trading station, thegateway, and the router may still communicate over a local area network,but the router may communicate with the matching process at theelectronic exchange through another connection means besides a T1, T3,or ISDN. In yet another example illustration, the gateway may be housedat, or near, its corresponding electronic exchange. According to thisinstance, the client device may communicate with the gateway over a widearea network or through the use of a T1, T3, ISDN, or some other highspeed connection.

Further, the gateway may be located remote from the client device andremote from the electronic exchange, which might be particularly usefulin systems that include interconnection of multiple trading networks.Thus, one trading network might have gateway access to an electronicexchange. Then, other trading networks may communicate with the tradingnetwork that has gateway access through a T1, T3, ISDN, or some otherhigh speed connection.

II. A Second Example Trading System

FIG. 2 illustrates another example trading system that uses similarcomputer elements as shown in FIG. 1, in which a trader may access andtrade at multiple electronic exchanges. The system comprises a clientdevice 202 that can access multiple electronic exchanges 204 and 208. Inthis particular embodiment, electronic exchange 204 is accessed throughgateway 206 and electronic exchange 208 is accessed through anothergateway 210. Alternatively, a single gateway may be programmed to handlemore than one electronic exchange. Router 212 is used to route messagesbetween the gateways 206 and 210 and the electronic exchanges 204 and208. While not shown in the figure, the system may include other devicesthat are specific to the client site like middleware and securitymeasures like firewalls, hubs, security managers, and so on, asunderstood by a person skilled in the art. Additional electronicexchanges may be added to the system so that the trader can trade at anynumber of exchanges, if so desired.

The trading system presented in FIG. 2 provides the trader with theopportunity to trade tradeable objects listed at different electronicexchanges. To some traders, there can be many advantages with amulti-exchange environment. For example, a trader could view marketinformation from each tradeable object through one common visualdisplay. As such, price and quantity information from the two separateexchanges may be presented together so that the trader can view bothmarkets simultaneously in the same window. In another example, a tradercan spread trade different tradeable objects listed at the differentelectronic exchanges.

As indicated earlier, one skilled in the art of electronic tradingsystems will understand that the present embodiments are not limited tothe particular configurations illustrated and described with respect toFIG. 1 and FIG. 2, and will be able to design a particular system basedon the specific requirements (for example, by adding additionalexchanges, gateways, client devices, routers, or other computers servingvarious functions like message handling and security). Additionally,several networks, like either of the networks shown in FIG. 1 or FIG. 2,may be linked together to communicatively access one or more electronicexchanges.

III. Client Device

Client devices 102 and 202 can be computers, such as a workstation,desktop, laptop, handheld device, and so forth, that allow a trader totrade one or more tradeable objects that are offered at exchange(s). Aclient device may include at least processor and memory. Preferably, theprocessor has enough processing power to handle and process varioustypes of market information. The more market information is received andprocessed, the more processing power is preferred.

Memory may include a computer readable medium. The term computerreadable medium, as used herein, refers to any medium that participatesin providing instructions to a processor unit for execution. Such amedium may take many forms, including but not limited to, nonvolatilemedia, and transmission media. Non-volatile media include, for example,optical or magnetic discs, such as storage devices. Volatile mediainclude, for example, dynamic memory, such as main memory or randomaccess memory (“RAM”). Common forms of computer readable media include,for example, floppy discs, flexible disks, hard discs, magnetic tape,punch cards, CD-ROM, any other physical medium, memory chip orcartridge, or any other medium from which a computer can read.

When a client device receives market information or other data, such asnews, or charting data, and order related information from an exchange,the received information may be displayed to the trader(s) on the visualoutput device or display device. However, it should be understood thatthe information could be provided to a trader using other means such assound. The output device can be any display device.

Upon viewing the market information or a portion thereof, a trader maywish to send orders to an exchange, cancel orders, change orders, queryan exchange, and so on. To do so, the trader may input various commandsor signals into a client device such as by typing into a keyboard,inputting commands through a mouse, or inputting commands or signalsthrough some other input device. For instance, a trader may click amouse button to initiate an order to buy a particular quantity of thetradeable object at a particular price. Then, a client device preferablygenerates transaction information. There are many different types ofmessages and/or order types that can be submitted, all of which may beconsidered various types of transaction information. Once generated,transaction information is sent from a client device to one or moreelectronic exchanges over communication links.

In one example embodiment, a client device uses software to createspecialized interactive trading screens on terminals associated withthem. Trading screens preferably enable traders to, among other things,enter and execute orders, obtain market quotes, and monitor positions.The range and quality of features available to the trader on his or hertrading screen may vary according to the specific software applicationbeing run. In addition to or in place of the interactive tradingscreens, a client device could run automated types of tradingapplications.

IV. Message Flow Diagram

FIG. 3 is a flow diagram illustrating an example operation of eithersystem shown in FIG. 1 or FIG. 2. This message flow diagram provides anexample of the flow of market information message by which a usercommunicates with the electronic exchange, receives market informationmessages for a selected tradeable object, and trades the tradeableobject. FIG. 3 includes an electronic exchange 302, a gateway or networkdevice 304, and a client device 306.

According to an example embodiment, a trader opens a trading applicationon the client device 306, which allows the trader to subscribe to trade,send, and receive market information message requests associated withone or more tradeable objects that are listed at the electronic exchange302. For example, the client device 306 may request market informationor make an order request to the gateway 304 and/or the electronicexchange 302. Market information may include any information associatedwith the tradeable object, including the best bid price, the best askprice, the last traded price, other prices outside of the best bid priceand ask price, quantities at those given prices, closing price, andsettlement price. The actual contents of the message may often depend onthe actual electronic exchange or the tradeable object itself.

According to the example embodiments, in response to the satisfied firstcondition, such as a trader selecting a contract in which to place anorder, the client device 306 may pre-marshall an order request messageto be sent to the gateway 304. Until the trader is ready to actuallymake the order request, the pre-marshalled order request message isstored in memory at the client device 306. Once the trader decides toactually submit the order request, thus satisfying the second condition,the pre-marshalled message will be sent to the gateway 304. A variety ofmessage requests can be pre-marshalled at the client device 306. Forexample, the trading system can assume that the trader will besubmitting order requests, market information requests, and even marketdepth requests associated with the tradeable objects that are beingtraded. Pre-marshalling these types of message requests saves the clientdevice processing time when the trader decides to actually request thatinformation. Additionally, submitting order requests to the exchange ata faster rate will allow for better queue position, and higherlikelihood of the trader's order getting filled.

Another defined first condition may be to pre-marshall messages uponboot up or login to a trading application. This condition may allow forpossible messages to be pre-marshalled and saved in memory before thetrader starts trading or a gateway starts receiving messages. In thisinstance, the trading system may pre-marshall the messages based on thetrader's past trading history or configuration files.

It should also be understood that unused or un-needed pre-marshalledmessage requests may be handled in a variety of ways. Specifically,unused pre-marshalled messages may be deleted from memory, such thatmemory is not taken up by messages that will go unused. In anotherexample, the unused pre-marshalled messages may be saved in memory andthen overwritten by the trading system. This method saves the tradingsystem from allocating and de-allocating memory with each pre-marshalledmessage. Whether or not unused pre-marshalled messages should be deletedor not may be configurable by the user.

According to another example embodiment, the gateway 304 pre-marshallsan acknowledgement, rejected, and/or error reply message in response tothe order request message that was received from the client device.These pre-marshalled messages are also stored in memory until a secondcondition is satisfied. The gateway 304 may then forward the orderrequest message onto the electronic exchange 302 which will thencommunicate the appropriate message back to the gateway 304. The gateway304 will receive and process the message. Once the message is receivedat the gateway 304 from the electronic exchange 302, the appropriatepre-marshalled message is retrieved from memory, any further up to datemarket information is added to the message, and then the message isimmediately sent to the client device, thus reducing the processing timeand resources needed to actually create and send the reply message tothe client device. Depending on the type of message request sent by theclient device 306, the gateway 304 could send back order fillinformation or other market information.

It should also be understood that the gateway 304 may also pre-marshallmessages to be sent to the electronic exchange. For example, the gatewaymay pre-marshall message requests and acknowledgments to be sent fromthe gateway to the electronic exchange.

In an additional embodiment, in response to an order request made by theclient device 306, the gateway 304 may pre-marshall multiple messagescorresponding to the different responses that the electronic exchange302 could send. For example, the gateway 304 may allocate a separate,unused, or under-utilized processing thread to pre-marshall an “orderfilled” reply message or an “order cancelled” reply message and storethem in memory.

In another example embodiment, processing time may be decreased andmessage size may be reduced by pre-marshalling partially completemessages replies and requests. For example, the gateway 304 may assumethat the order will get filled eventually, so gateway 304 sends apartially complete “order will be filled” message to the client device306. Once the electronic exchange 302 replies with the complete orderfill information, such as fill price and quantity, the gateway 304 canthen create and reply with another smaller message that includes theupdated order fill market information, therefore taking up lessbandwidth.

These partially complete messages may be marked as “preliminary” beforebeing sent to/from the client device 306, such that the client device306 or the gateway 304 are aware that a more complete or “final” messagewill be sent shortly. In this case, the client device 306 may store the“preliminary” message in memory until the “final” message with theupdated order fill market information arrives. The preliminary and finalmessages may be associated with each other based on a unique ID or orderkey. This unique ID or order key will be associated with both thepreliminary and the final message. Once a final message is sent, theclient device and/or network device may delete any corresponding unusedpre-marshalled messages that were stored in memory or save the messagesand overwrite them with the next pre-marshalled message.

It should also be understood that the messages that are pre-marshalledby the trading system must also be un-marshalled when they are receivedat their final destination. Pre-marshalling a message can include somesort of encryption, and un-marshalling a message may include decryptionof the pre-marshalled message. Un-marshalling a message transforms themessage into a form that is useable the receiver of the message.

V. Pre-Marshalling Messages

FIG. 4 is a flow chart illustrating an example method forpre-marshalling messages in an electronic trading environment. It shouldbe understood that the flow chart only shows the functionality andoperation of a possible implementation of the present embodiments. Inthis regard, each block may represent a module, a segment, or a portionof the program code, which includes one or more executable instructionsfor implementing specific logical functions or steps in the process.Alternative implementations are included within the scope of the exampleembodiments of the present invention in which functions may be executedout of order from that shown or discussed, including substantiallyconcurrent or in reverse order, depending on the functionality involved,as would be understood by those reasonably skilled in the art of thepresent invention.

At step 402, one or more first conditions for creating pre-marshalledmessages are defined. A first condition, for example, may be a messagerequest being received from the client device at the gateway. Themessage request may consist of, for example, an order request, an orderdeletion/cancellation, or a request for updated market information.Additionally, a condition may be an action by the trader, for example,the selection of a contract for which an order may be placed in, ormarket information may be requested for. Another example definedcondition may be a trader logging into the trading system or perhapsboot up of a computer device such as a client or network device. Thetrading system may also anticipate the types of messages that may bepre-marshalled based on near term or long term trading history orconfiguration files.

Additionally, at step 402, one or more second conditions for determiningwhen to send the pre-marshalled messages are defined. A secondcondition, for example, may be an additional message request beingreceived from the client device at the gateway. A second condition mayalso be the submission of an order request, submission or orderdeletion/cancellation, a need for an acknowledgement or error message,updated market information, or an order getting filled at the electronicexchange.

At step 404, the device determines if the first condition has beensatisfied.

At step 406, based on the satisfied first condition, different types ofmessages are pre-marshalled with the market information known at thattime.

At step 408, the pre-marshalled messages are stored in memory until thesecond condition is satisfied.

At step 410, the device determines if the second condition has beensatisfied.

At step 412, based on the satisfied second condition and the marketinformation known at that time, the device determines whichpre-marshalled message needs further market information appended inorder to create a complete message.

At step 414, the device sends the appropriate pre-marshalled message.Once the pre-marshalled message is sent, the unused pre-marshalledmessage can be deleted or saved.

At step 416, the pre-marshalled message is deleted from memory. Aspreviously stated, the user may configure whether or not pre-marshalledmessage are deleted or saved and overwritten by the trading system.

CONCLUSION

The example embodiments discussed above describe a method forpre-marshalling messages in an electronic trading environment.Specifically, pre-marshalling messages allows for client devices andnetwork devices to create messages in response to a defined firstcondition. A first condition may be defined, for example, as any messagereceived from the client device or the network device, or an actiontaken by a trader. Pre-marshalling reply messages also allows a tradingsystem to do more processing up front before the message is needed, suchthat when the message is actually needed no further or very littleprocessing must be performed at the client or network device. Anotherexample defined first condition may be that pre-marshalled messages arecreated upon login or boot up, where the pre-marshalled messages arebased on trading history or a configuration file.

Based on the type of message that is received from the client device,the network device will assign a separate, unused, or under-utilizedprocessing thread to the task of creating pre-marshalled reply messages.Similarly, based on the type of action taken by the trader, the clientdevice will assign a processing thread the task of creatingpre-marshalled message requests. The pre-marshalled messages may bestored in memory until it is determined that a message should be sent,or when a second condition is satisfied. A second condition may bedefined, for example as the receipt of another message or reply from thenetwork. A second condition may also be the submission of an orderrequest, submission or order deletion/cancellation, a need for anacknowledgement or error message, updated market information, or anorder getting filled at the electronic exchange.

A pre-marshalled message may be considered a preliminary message whenonly partially complete market information is available at that time.Once further market information is known, the trading system willassociate the corrected market information with the final message basedon a unique ID or a unique order key. This unique ID or order key willbe associated with both the preliminary and the final message. Once afinal message is sent, the client device and/or network device maydelete any corresponding unused pre-marshalled messages that were storedin memory or save the messages and overwrite them with the subsequentpre-marshalled message.

Due to messages being pre-marshalled, processing resources are savedwhen it is actually time to send a pre-marshalled message. As previouslydiscussed, conventionally, the message requests or replies would not becreated until a message was needed. The conventional method takes upmore processing time and resources when it is of the utmost importanceto send a message as quickly as possible. Pre-marshalling allows forfaster processing of messages, which may lead to many advantages such asbetter queue position for the trader, faster response time to marketchanges, etc.

The above description of the example embodiments, alternativeembodiments, and specific examples, are given by way of illustration andshould not be viewed as limiting. Further, many changes andmodifications within the scope of the present embodiments may be madewithout departing from the spirit thereof, and the present inventionincludes such changes and modifications.

It will be apparent to those of ordinary skill in the art that methodsinvolved in the system and method for pre-marshalling messages in anelectronic trading environment may be embodied in a computer programproduct that includes one or more computer readable media. For example,a computer readable medium can include a readable memory device, such asa hard drive device, CD-ROM, a DVD-ROM, or a computer diskette, havingcomputer readable program code segments stored thereon. The computerreadable medium can also include a communications or transmissionmedium, such as, a bus or a communication link, either optical, wired orwireless having program code segments carried thereon as digital oranalog data signals.

The claims should not be read as limited to the described order orelements unless stated to that effect. Therefore, all embodiments thatcome within the scope and spirit of the following claims and equivalentsthereto are claimed as the invention.

1. (canceled)
 2. A method for submitting electronic orders in anelectronic trading message in an electronic trading environment, themethod comprising: detecting, via a computing device, a first conditionfor determining whether to assemble a first portion of an electronicorder for a tradeable object, the electronic order having at least afirst portion and a second portion; in response to detecting the firstcondition, assembling, via the computing device, the first portion forthe electronic order for the tradeable object; storing, via thecomputing device, the electronic order with the first portion andwithout the second portion of the electronic order, where the storedelectronic order with the first portion is incomplete; detecting, viathe computing device, a second condition for transmitting the electronicorder to an electronic exchange; and in response to detecting the secondcondition: assembling, via the computing device, the second portion ofthe electronic order for the tradeable object according to a second setof information available at a second time, appending, via the computingdevice, the second portion of the electronic order to the storedincomplete electronic order with the first portion to generate acomplete electronic order for the tradeable object, where the completeelectronic order includes at least the first portion and the secondportion, and sending the complete electronic order to the electronicexchange.
 3. The method of claim 2 where the complete electronic ordercomprises an order request message.
 4. The method of claim 3 where thesecond condition comprises a trader submitting the order request messageand the second portion comprises price information for the tradeableobject selected by the trader at the second time.
 5. The method of claim2 where the complete electronic order comprises a delete order message.6. The method of claim 5 where the second condition comprises a triggerto send the delete order message.
 7. The method of claim 2 where thefirst condition comprises a login at the computing device.
 8. The methodof claim 2 where the first condition comprises a user selection of atradeable object via the computing device.
 9. The method of claim 2where the computing device comprises a client device.
 10. The method ofclaim 2 where the computing device comprises a network device.
 11. Themethod of claim 2 where the first condition comprises sending anelectronic trading message.
 12. The method of claim 2 where the firstportion comprises a preliminary message associated with a uniqueidentification number.
 13. The method of claim 12 where the secondportion comprises a final message also associated with the uniqueidentification number.
 14. The method of claim 2, further comprisingdeleting the stored electronic order with the first portion and withoutthe second portion of the electronic order in response to the secondcondition being satisfied.
 15. A non-transient computer readable mediumhaving program code stored therein for execution by a computing device,the program code comprising: a first program code for detecting a firstcondition for determining whether to assemble a first portion of anelectronic order for a tradeable object, the electronic order having atleast a first portion and a second portion; a second program code forassembling the first portion for the electronic order for the tradeableobject according to a first set of information available at a first timein response to detecting the first condition; a third program code forstoring the electronic order with the first portion and without thesecond portion of the electronic order, where the stored electronicorder with the first portion is incomplete; a fourth program code fordetecting a second condition for transmitting the electronic order to anelectronic exchange; and a fifth program code, which in response todetecting the second condition is configured for: assembling, via thecomputing device, the second portion of the electronic order for thetradeable object according to a second set of information available at asecond time, appending, via the computing device, the second portion ofthe electronic order to the stored incomplete electronic order with thefirst portion to generate a complete electronic order for the tradeableobject, where the complete electronic order includes at least the firstportion and the second portion, and sending the complete electronicorder to the electronic exchange.
 16. The non-transient computerreadable medium of claim 15 where the complete electronic ordercomprises an order request message.
 17. The non-transient computerreadable medium of claim 16 where the second condition comprises atrader submitting the order request message and the second portioncomprises price information for the tradeable object selected by thetrader at the second time.
 18. The non-transient computer readablemedium of claim 15 where the complete electronic order comprises adelete order message.
 19. The non-transient computer readable medium ofclaim 18 where the second condition comprises a trigger to send thedelete order message.
 20. The non-transient computer readable medium ofclaim 15 where the first condition comprises a login at the computingdevice.
 21. The non-transient computer readable medium of claim 15 wherethe first condition comprises a user selection of a tradeable object viathe computing device.
 22. The non-transient computer readable medium ofclaim 15 where the computing device comprises a client device.
 23. Thenon-transient computer readable medium of claim 15 where the computingdevice comprises a network device.
 24. The non-transient computerreadable medium of claim 15 where the first condition comprises sendingan electronic trading message.
 25. The non-transient computer readablemedium of claim 15 where the first portion comprises a preliminarymessage associated with a unique identification number.
 26. Thenon-transient computer readable medium of claim 25 where the secondportion comprises a final message also associated with the uniqueidentification number.
 27. The non-transient computer readable medium ofclaim 15 where the stored electronic order with the first portion andwithout the second portion of the electronic order is deleted inresponse to the second condition being satisfied.